home *** CD-ROM | disk | FTP | other *** search
- Any questions -> brisco@pilot.njin.net
-
- This is the PRODUCTION distribution of the SETTRANSFER code. The
- SETTRANSFER code permits the use of the keyword "transfer" to specify
- alternate programs to do the zone transfer if the current named is a
- secondary nameserver for a zone.
-
- The details on using alternative zone transfer mechanisms as a
- means for achieving load balancing is described in an internet draft
- "draft-ietf-dns-lb-00.txt", and is currently (12/1/94) under review
- for publishing as an informational RFC. The draft is available from
- ds.internic.net via anonymous ftp.
-
- Primarily the code changes adds enough syntax to do a database
- style lookup based on the zone name (nothing fancy, just an array),
- and to execute that program. Some necessary other changes were done
- in order to support ordered, quickly changing address records -
- primarily this had to do with lowering the value of static variables
- putting rather high minimum values in for the minimum zone refresh
- period, and minimum TTL associated with records. Additionally, in
- order to preserve the ordering of the records, all references to RR
- ordering are ifdef'd out. Also note that this, and Round Robin
- ordering are mutually exclusive.
-
- Specific changes are detailed in the file SETTRANSFER_CHANGES.
-
- Example configurations (and diffs to older versions of BIND) are
- available via anonymous ftp from pilot.njin.net:pub/TRANSFER.
-
-
- Currently (as of 2/22/94) there is a "fast" subdomain
- eden.rutgers.edu running on the NS for eden.rutgers.edu ("eden" is a
- subzone of rutgers.edu). It uses the code from the LOADSAMP.shar to
- balance the load amongst seven SparcCenter 1000s. This is in active
- use in the Rutgers University domain.
-